Wait for the job, not the whole queue - #7997
Merged
Merged
Conversation
labkey-adam
approved these changes
Aug 31, 2026
labkey-adam
left a comment
labkey-adam
left a comment
Contributor
There was a problem hiding this comment.
Are there other callers that should be migrated?
Contributor
Author
Collaborator
|
@labkey-jeckels, huh, that's interesting. I dont think I've seen the 'wait for whole queue behavior', but I will look at this. |
Contributor
Author
Your use cases may not trigger calls to |
Collaborator
|
OK. In any case, these are all simple to migrate. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rationale
JobRunner.waitForCompletion()blocks until all jobs in the queue have completed, including those that are scheduled for future execution. That can be a long wait. Most callers want to wait until their job is complete.Changes
Tasks